Summary

• Add a new notification plugin for Flowtriq, a DDoS detection and traffic analytics platform
• The plugin POSTs alert payloads (JSON) to a configurable webhook URL with optional API key authentication via X-API-Key header
• Follows the same patterns as existing webhook-based plugins (Slack, VictorOps, PagerDuty)

What's included

Plugin logic (cmk/notification_plugins/flowtriq.py):

• Builds a JSON payload with source, host, host_address, service, state, output, notification_type, and optional Checkmk url
• Sends via post_request with optional X-API-Key header
• Accepts 200, 201, and 202 as success status codes

Entry point script (notifications/flowtriq.py):

• Standard notification script entry point following existing patterns

WATO GUI form (cmk/gui/wato/_notification_parameter/_flowtriq.py):

• Webhook URL (explicit or from password store)
• Optional API key (stored securely via Checkmk password handling)
• SSL verification toggle, proxy, and URL prefix settings

Type definitions (cmk/utils/notify_types.py):

• FlowtriqPluginModel, FlowtriqPluginName, FlowtriqNotify
• Added to KnownPluginParameters, BuiltInPluginNames, NotifyPluginParamsDict unions

Tests:

• Unit tests covering service notification, host notification, and recovery scenarios
• Updated test_registry, test_configuration_entity, and test_binaries expected plugin lists

Build:

• Added to Bazel BUILD notification_scripts pkg_files renames

Test plan

• Unit tests pass for test_flowtriq.py (message construction for service, host, and recovery notifications)
• Notification parameter registry test includes flowtriq
• Configuration entity readable name resolves to "Flowtriq parameter"
• Integration binary smoke test exits with expected KeyError.*NOTIF when run without env vars
• End-to-end: configure Flowtriq notification in WATO, trigger a test notification, verify JSON payload arrives at webhook endpoint